Screen recording camera mode

ABSTRACT

A messaging system, which hosts a backend service for a messaging client, includes a screen recording system configured to improve usability of a screen recording process while preserving users&#39; privacy in the messaging system. Privacy is preserved by removing the foreground focus from the messaging client when screen recording is in progress. Screen recording is automatically paused when the screen recording system detects a request to restore the foreground focus to the messaging client.

PRIORITY CLAIM

This application is a continuation of and claims the benefit of priorityof U.S. patent application Ser. No. 16/949,597, filed Nov. 5, 2020,which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to facilitating interactionsbetween client devices over a network.

BACKGROUND

The popularity of computer-implemented tools that permit users to accessand interact with content and other users online continues to grow. Forexample, users can share content captured by a camera, such as imagesand video (referred to as camera sharing), as well as text, andreferences to web pages (referred to as non-camera sharing). An exampleof a computer-implemented tool is a messaging app configured to permitusers to share and exchange data and that may include functionality thatpermits users to capture content, using a camera provided with theclient device, from within the app, provided a user granted permissionto an app to access the camera.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. To easily identifythe discussion of any particular element or act, the most significantdigit or digits in a reference number refer to the figure number inwhich that element is first introduced. Some examples are illustrated byway of example, and not limitation, in the figures of the accompanyingdrawings in which:

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexamples.

FIG. 2 is a diagrammatic representation of a messaging system, inaccordance with some examples, that has both client-side and server-sidefunctionality.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some examples.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome examples.

FIG. 5 is a flowchart for an access-limiting process, in accordance withsome examples.

FIG. 6 is a flowchart of a method for facilitating screen recordingcamera mode, in accordance with some examples.

FIG. 7 is a diagram illustrating an example camera view screen includinga screen recording user selectable element.

FIG. 8 is a diagram illustrating an example dialog presented to obtain auser's permission to commence screen recording.

FIG. 9 is a diagram illustrating an example dialog presented to obtain auser's instruction to resume or to stop screen recording.

FIG. 10 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed herein, in accordance with some examples.

DETAILED DESCRIPTION

Embodiments of the present disclosure improve the functionality ofelectronic messaging software and systems by enhancing usability of ascreen recording process while preserving users' privacy in a messagingsystem. As mentioned above, users can share content captured by acamera, as well non-camera content. An example of non-camera content isa recording of the output of the display system shown on the screen ofthe client device, e.g., a recording of a computer game played by auser. While it may be appealing to users to record their activity at amobile device and to share it in a way that the recipient would be ableto see a video of a screen sequence the way it was experienced by thesending user, facilitating screen recording may become problematic if arecording of a user's activity includes the recording of their viewingof ephemeral messages configured to not persist after having been viewedby the recipient.

The technical problem of enhancing usability of a screen recordingprocess while preserving users' privacy in a messaging system isaddressed by providing a screen recording functionality as a camera modeselectable from a camera view user interface. The camera view userinterface may be displayed by a messaging client executing at a clientdevice, when the messaging client is in the foreground of the screen ofthe client device. A camera view user interface is configured to displayoutput of a digital image sensor of a camera provided with an associatedclient device and also to display various user selectable elements, suchas a user selectable element that is actionable to capture an image bythe camera or to start and stop video recording, and such as varioususer selectable elements actionable to set respective camera modes,e.g., a timer mode or flash mode.

A screen recording system is configured to include, in a camera viewuser interface, a user selectable element, termed a screen recorder userselectable element, actionable to request recording of an output of adisplay system shown on a screen of the client device. When a user tapson or otherwise activates the screen recorder user selectable elementand confirms the instruction to commence screen recording, the screenrecording system removes the foreground focus from the messaging clientand causes to commence the recording of the output of the display systemshown on the screen of the client device. For the purposes of thisdescription, the operation of removing the foreground focus from an appexecuting at a client device is termed backgrounding. Once the screenrecording starts, the output of the display system shown on the screenof the client device is being recorded while the user is interactingwith the client device, e.g., by playing a game, checking the weather ata weather app, or reading the news.

The screen recording is automatically paused once the screen recordingsystem detects a request to open or to bring to the foreground themessaging client. A request to open or to bring to the foreground themessaging client may be, e.g., in the form of activating a notificationfrom the messaging client, activating an icon representing the messagingclient on the screen of the client device, or selecting the messagingclient from one or more apps executing in the background. When thescreen recording is automatically paused in response to a detectedrequest to open or to bring to the foreground the messaging client, thescreen recording system opens the messaging client with the screen ofthe messaging client blacked out, and also presents on the screen of theclient device a dialog requesting the user to select to continue withthe screen recording, in which case the messaging client is backgroundedagain, or to stop screen recording.

If the screen recording system receives the user's selection of stoppingthe screen recording, the screen recording system stops the screenrecording and causes presentation, at the messaging client, a userinterface for saving and/or editing of the video recorded during thescreen recording process. The video of screen recording saved in themessaging system can be shared with other users of the messaging system.If the screen recording system detects the user's selection of resumingthe screen recording, the screen recording system once again removes theforeground focus of the screen of the client device from the messagingclient and resumes screen recording.

Networked Computing Environment

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network,within which a screen recording system can be implemented. The messagingsystem 100 includes multiple instances of a client device 102, each ofwhich hosts a number of applications, including a messaging client 104.Each messaging client 104 is communicatively coupled to other instancesof the messaging client 104 and a messaging server system 108 via anetwork 106 (e.g., the Internet).

A messaging client 104 is able to communicate and exchange data withanother messaging client 104 and with the messaging server system 108via the network 106. The data exchanged between messaging client 104,and between a messaging client 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client 104. While certainfunctions of the messaging system 100 are described herein as beingperformed by either a messaging client 104 or by the messaging serversystem 108, the location of certain functionality either within themessaging client 104 or the messaging server system 108 may be a designchoice. For example, it may be technically preferable to initiallydeploy certain technology and functionality within the messaging serversystem 108 but to later migrate this technology and functionality to themessaging client 104 where a client device 102 has sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client 104. Such operations includetransmitting data to, receiving data from, and processing data generatedby the messaging client 104. This data may include message content,client device information, geolocation information, media augmentationand overlays, message content persistence conditions, social networkinformation, and live event information, as examples. Data exchangeswithin the messaging system 100 are invoked and controlled throughfunctions available via user interfaces (UIs) of the messaging client104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, application servers 112. Theapplication servers 112 are communicatively coupled to a database server118, which facilitates access to a database 120 that stores dataassociated with messages processed by the application servers 112.Similarly, a web server 124 is coupled to the application servers 112,and provides web-based interfaces to the application servers 112. Tothis end, the web server 124 processes incoming network requests overthe Hypertext Transfer Protocol (HTTP) and several other relatedprotocols.

The Application Program Interface (API) server 110 receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application servers 112. Specifically, theApplication Program Interface (API) server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client 104 in order to invoke functionality of theapplication servers 112. The Application Program Interface (API) server110 exposes various functions supported by the application servers 112,including account registration, login functionality, the sending ofmessages, via the application servers 112, from a particular messagingclient 104 to another messaging client 104, the sending of media files(e.g., images or video) from a messaging client 104 to a messagingserver 114, and for possible access by another messaging client 104, thesettings of a collection of media data (e.g., story), the retrieval of alist of friends of a user of a client device 102, the retrieval of suchcollections, the retrieval of messages and content, the addition anddeletion of entities (e.g., friends) to an entity graph (e.g., a socialgraph), the location of friends within a social graph, and opening anapplication event (e.g., relating to the messaging client 104).

The application servers 112 host a number of server applications andsubsystems, including for example a messaging server 114, an imageprocessing server 116, and a social network server 122. The messagingserver 114 implements a number of message processing technologies andfunctions, particularly related to the aggregation and other processingof content (e.g., textual and multimedia content) included in messagesreceived from multiple instances of the messaging client 104. Otherprocessor and memory intensive processing of data may also be performedserver-side by the messaging server 114, in view of the hardwarerequirements for such processing.

The application servers 112 also include an image processing server 116that is dedicated to performing various image processing operations,typically with respect to images or video within the payload of amessage sent from or received at the messaging server 114.

The social network server 122 supports various social networkingfunctions and services and makes these functions and services availableto the messaging server 114. To this end, the social network server 122maintains and accesses an entity graph 306 (as shown in FIG. 3) withinthe database 120. Examples of functions and services supported by thesocial network server 122 include the identification of other users ofthe messaging system 100 with which a particular user has relationshipsor is “following,” and also the identification of other entities andinterests of a particular user.

A screen recording system can be implemented as a service or a systemspanning the messaging client 104 and the messaging server system 108.For example, the generating of various user interfaces may be performedat the messaging server system 108 and communicated to the messagingclient 104. Alternatively, at least some of the user interfaces may begenerated by the messaging client 104. Furthermore, the detecting ofactivation of various user selectable elements may be at the performedat the messaging client 104 and communicated to the messaging serversystem 108. Further details regarding a screen recording system arediscussed below.

System Architecture

FIG. 2 is a block diagram illustrating further details regarding themessaging system 100, within which a screen recording system may beimplemented, according to some examples. Specifically, the messagingsystem 100 is shown to comprise the messaging client 104 and theapplication servers 112. The messaging system 100, which embodies anumber of subsystems that are supported on the client-side by themessaging client 104 and on the sever-side by the application servers112, can be said to host a backend service for the messaging client 104.These subsystems include, for example, an ephemeral timer system 202, acollection management system 204, an augmentation system 206, a mapsystem 208, and a game system 210.

The ephemeral timer system 202 is responsible for enforcing thetemporary or time-limited access to content by the messaging client 104and the messaging server 114. The ephemeral timer system 202incorporates a number of timers that, based on duration and displayparameters associated with a message, or collection of messages (e.g., astory), selectively enable access (e.g., for presentation and display)to messages and associated content via the messaging client 104. Furtherdetails regarding the operation of the ephemeral timer system 202 areprovided below.

The collection management system 204 is responsible for managing sets orcollections of media (e.g., collections of text, image video, and audiodata). A collection of content (e.g., messages, including images, video,text, and audio) may be organized into an “event gallery” or an “eventstory.” Such a collection may be made available for a specified timeperiod, such as the duration of an event to which the content relates.For example, content relating to a music concert may be made availableas a “story” for the duration of that music concert. The collectionmanagement system 204 may also be responsible for publishing an iconthat provides notification of the existence of a particular collectionto the user interface of the messaging client 104.

The collection management system 204 furthermore includes a curationinterface 212 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface212 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certain examples,compensation may be paid to a user for the inclusion of user-generatedcontent into a collection. In such cases, the collection managementsystem 204 operates to automatically make payments to such users for theuse of their content.

The augmentation system 206 provides various functions that enable auser to augment (e.g., annotate or otherwise modify or edit) mediacontent associated with a message. For example, the augmentation system206 provides functions related to the generation and publishing of mediaoverlays for messages processed by the messaging system 100. Theaugmentation system 206 operatively supplies a media overlay oraugmentation (e.g., an image filter) to the messaging client 104 basedon a geolocation of the client device 102. In another example, theaugmentation system 206 operatively supplies a media overlay to themessaging client 104 based on other information, such as social networkinformation of the user of the client device 102. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying. Theaudio and visual content or the visual effects can be applied to a mediacontent item (e.g., a photo) at the client device 102. For example, themedia overlay may include text or image that can be overlaid on top of aphotograph taken by the client device 102. In another example, the mediaoverlay includes an identification of a location overlay (e.g., Venicebeach), a name of a live event, or a name of a merchant overlay (e.g.,Beach Coffee House). In another example, the augmentation system 206uses the geolocation of the client device 102 to identify a mediaoverlay that includes the name of a merchant at the geolocation of theclient device 102. The media overlay may include other indiciaassociated with the merchant. The media overlays may be stored in thedatabase 120 and accessed through the database server 118.

In some examples, the augmentation system 206 provides a user-basedpublication platform that enables users to select a geolocation on a mapand upload content associated with the selected geolocation. The usermay also specify circumstances under which a particular media overlayshould be offered to other users. The augmentation system 206 generatesa media overlay that includes the uploaded content and associates theuploaded content with the selected geolocation.

In other examples, the augmentation system 206 provides a merchant-basedpublication platform that enables merchants to select a particular mediaoverlay associated with a geolocation via a bidding process. Forexample, the augmentation system 206 associates the media overlay of thehighest bidding merchant with a corresponding geolocation for apredefined amount of time.

The map system 208 provides various geographic location functions, andsupports the presentation of map-based media content and messages by themessaging client 104. For example, the map system 208 enables thedisplay of user icons or avatars (e.g., stored in profile data 308) on amap to indicate a current or past location of “friends” of a user, aswell as media content (e.g., collections of messages includingphotographs and videos) generated by such friends, within the context ofa map. For example, a message posted by a user to the messaging system100 from a specific geographic location may be displayed within thecontext of a map at that particular location to “friends” of a specificuser on a map interface of the messaging client 104. A user canfurthermore share his or her location and status information (e.g.,using an appropriate status avatar) with other users of the messagingsystem 100 via the messaging client 104, with this location and statusinformation being similarly displayed within the context of a mapinterface of the messaging client 104 to selected users.

The game system 210 provides various gaming functions within the contextof the messaging client 104. The messaging client 104 provides a gameinterface providing a list of available games that can be launched by auser within the context of the messaging client 104, and played withother users of the messaging system 100. The messaging system 100further enables a particular user to invite other users to participatein the play of a specific game, by issuing invitations to such otherusers from the messaging client 104. The messaging client 104 alsosupports both the voice and text messaging (e.g., chats) within thecontext of gameplay, provides a leaderboard for the games, and alsosupports the provision of in-game rewards (e.g., coins and items).

Also shown in FIG. 2 is a screen recording system 214. The screenrecording system 214 is configured to address the technical problem ofenhancing usability of a screen recording process while preservingusers' privacy in the messaging system. The screen recording system 214generates a camera view user interface including a screen recorder userselectable element, which is actionable to request recording of anoutput of a display system shown on a screen of a client device. When auser taps on or otherwise activates the screen recorder user selectableelement, the screen recording system removes the foreground focus fromthe messaging client and causes to commence the recording of the outputof the display system shown on the screen of the client device. Thescreen recording is automatically paused once the screen recordingsystem detects a request to bring the messaging client to theforeground.

Data Architecture

FIG. 3 is a schematic diagram illustrating data structures 300, whichmay be stored in the database 120 of the messaging server system 108,according to certain examples. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table302. This message data includes, for any particular one message, atleast message sender data, message recipient (or receiver) data, and apayload. Further details regarding information that may be included in amessage, and included within the message data stored in the messagetable 302 is described below with reference to FIG. 4.

An entity table 304 stores entity data, and is linked (e.g.,referentially) to an entity graph 306 and profile data 308. Entities forwhich records are maintained within the entity table 304 may includeindividuals, corporate entities, organizations, objects, places, events,and so forth. Regardless of entity type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 306 stores information regarding relationships andassociations between entities. Such relationships may be social,professional (e.g., work at a common corporation or organization)interested-based or activity-based, merely for example.

The profile data 308 stores multiple types of profile data about aparticular entity. The profile data 308 may be selectively used andpresented to other users of the messaging system 100, based on privacysettings specified by a particular entity. Where the entity is anindividual, the profile data 308 includes, for example, a user name,telephone number, address, settings (e.g., notification and privacysettings), as well as a user selected avatar representation (orcollection of such avatar representations). A particular user may thenselectively include one or more of these avatar representations withinthe content of messages communicated via the messaging system 100, andon map interfaces displayed by messaging clients 104 to other users. Thecollection of avatar representations may include “status avatars,” whichpresent a graphical representation of a status or activity that the usermay select to communicate at a particular time.

Where the entity is a group, the profile data 308 for the group maysimilarly include one or more avatar representations associated with thegroup, in addition to the group name, members, and various settings(e.g., notifications) for the relevant group.

The database 120 also stores augmentation data, such as overlays orfilters, in an augmentation table 310. The augmentation data isassociated with and applied to videos (for which data is stored in avideo table 314) and images (for which data is stored in an image table316).

Filters, in one example, are overlays that are displayed as overlaid onan image or video during presentation to a recipient user. Filters maybe of various types, including user selected filters from a set offilters presented to a sending user by the messaging client 104 when thesending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters), which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client 104, based ongeolocation information determined by a Global Positioning System (GPS)unit of the client device 102.

Another type of filter is a data filter, which may be selectivelypresented to a sending user by the messaging client 104, based on otherinputs or information gathered by the client device 102 during themessage creation process. Examples of data filters include currenttemperature at a specific location, a current speed at which a sendinguser is traveling, battery life for a client device 102, or the currenttime.

Other augmentation data that may be stored within the image table 316includes augmented reality content items (e.g., corresponding toapplying Lenses or augmented reality experiences). An augmented realitycontent item may be a real-time special effect and sound that may beadded to an image or a video.

As described above, augmentation data includes augmented reality contentitems, overlays, image transformations, AR images, and similar termsrefer to modifications that may be applied to image data (e.g., videosor images). This includes real-time modifications, which modify an imageas it is captured using device sensors (e.g., one or multiple cameras)of a client device 102 and then displayed on a screen of the clientdevice 102 with the modifications. This also includes modifications tostored content, such as video clips in a gallery that may be modified.For example, in a client device 102 with access to multiple augmentedreality content items, a user can use a single video clip with multipleaugmented reality content items to see how the different augmentedreality content items will modify the stored clip. For example, multipleaugmented reality content items that apply different pseudorandommovement models can be applied to the same content by selectingdifferent augmented reality content items for the content. Similarly,real-time video capture may be used with an illustrated modification toshow how video images currently being captured by sensors of a clientdevice 102 would modify the captured data. Such data may simply bedisplayed on the screen and not stored in memory, or the contentcaptured by the device sensors may be recorded and stored in memory withor without the modifications (or both). In some systems, a previewfeature can show how different augmented reality content items will lookwithin different windows in a display at the same time. This can, forexample, enable multiple windows with different pseudorandom animationsto be viewed on a display at the same time.

Data and various systems using augmented reality content items or othersuch transform systems to modify content using this data can thusinvolve detection of objects (e.g., faces, hands, bodies, cats, dogs,surfaces, objects, etc.), tracking of such objects as they leave, enter,and move around the field of view in video frames, and the modificationor transformation of such objects as they are tracked. In variousembodiments, different methods for achieving such transformations may beused. Some examples may involve generating a three-dimensional meshmodel of the object or objects, and using transformations and animatedtextures of the model within the video to achieve the transformation. Inother examples, tracking of points on an object may be used to place animage or texture (which may be two dimensional or three dimensional) atthe tracked position. In still further examples, neural network analysisof video frames may be used to place images, models, or textures incontent (e.g., images or frames of video). Augmented reality contentitems thus refer both to the images, models, and textures used to createtransformations in content, as well as to additional modeling andanalysis information needed to achieve such transformations with objectdetection, tracking, and placement.

Real-time video processing can be performed with any kind of video data(e.g., video streams, video files, etc.) saved in a memory of acomputerized system of any kind. For example, a user can load videofiles and save them in a memory of a device, or can generate a videostream using sensors of the device. Additionally, any objects can beprocessed using a computer animation model, such as a human's face andparts of a human body, animals, or non-living things such as chairs,cars, or other objects.

In some examples, when a particular modification is selected along withcontent to be transformed, elements to be transformed are identified bythe computing device, and then detected and tracked if they are presentin the frames of the video. The elements of the object are modifiedaccording to the request for modification, thus transforming the framesof the video stream. Transformation of frames of a video stream can beperformed by different methods for different kinds of transformation.For example, for transformations of frames mostly referring to changingforms of object's elements characteristic points for each element of anobject are calculated (e.g., using an Active Shape Model (ASM) or otherknown methods). Then, a mesh based on the characteristic points isgenerated for each of the at least one element of the object. This meshused in the following stage of tracking the elements of the object inthe video stream. In the process of tracking, the mentioned mesh foreach element is aligned with a position of each element. Then,additional points are generated on the mesh. A first set of first pointsis generated for each element based on a request for modification, and aset of second points is generated for each element based on the set offirst points and the request for modification. Then, the frames of thevideo stream can be transformed by modifying the elements of the objecton the basis of the sets of first and second points and the mesh. Insuch method, a background of the modified object can be changed ordistorted as well by tracking and modifying the background.

In some examples, transformations changing some areas of an object usingits elements can be performed by calculating characteristic points foreach element of an object and generating a mesh based on the calculatedcharacteristic points. Points are generated on the mesh, and thenvarious areas based on the points are generated. The elements of theobject are then tracked by aligning the area for each element with aposition for each of the at least one element, and properties of theareas can be modified based on the request for modification, thustransforming the frames of the video stream. Depending on the specificrequest for modification properties of the mentioned areas can betransformed in different ways. Such modifications may involve changingcolor of areas; removing at least some part of areas from the frames ofthe video stream; including one or more new objects into areas which arebased on a request for modification; and modifying or distorting theelements of an area or object. In various embodiments, any combinationof such modifications or other similar modifications may be used. Forcertain models to be animated, some characteristic points can beselected as control points to be used in determining the entirestate-space of options for the model animation.

In some examples of a computer animation model to transform image datausing face detection, the face is detected on an image with use of aspecific face detection algorithm (e.g., Viola-Jones). Then, an ActiveShape Model (ASM) algorithm is applied to the face region of an image todetect facial feature reference points.

In other examples, other methods and algorithms suitable for facedetection can be used. For example, in some embodiments, features arelocated using a landmark, which represents a distinguishable pointpresent in most of the images under consideration. For facial landmarks,for example, the location of the left eye pupil may be used. If aninitial landmark is not identifiable (e.g., if a person has aneyepatch), secondary landmarks may be used. Such landmark identificationprocedures may be used for any such objects. In some examples, a set oflandmarks forms a shape. Shapes can be represented as vectors using thecoordinates of the points in the shape. One shape is aligned to anotherwith a similarity transform (allowing translation, scaling, androtation) that minimizes the average Euclidean distance between shapepoints. The mean shape is the mean of the aligned training shapes.

In some examples, a search for landmarks from the mean shape aligned tothe position and size of the face determined by a global face detectoris started. Such a search then repeats the steps of suggesting atentative shape by adjusting the locations of shape points by templatematching of the image texture around each point and then conforming thetentative shape to a global shape model until convergence occurs. Insome systems, individual template matches are unreliable, and the shapemodel pools the results of the weak template matches to form a strongeroverall classifier. The entire search is repeated at each level in animage pyramid, from coarse to fine resolution.

A transformation system can capture an image or video stream on a clientdevice (e.g., the client device 102) and perform complex imagemanipulations locally on the client device 102 while maintaining asuitable user experience, computation time, and power consumption. Thecomplex image manipulations may include size and shape changes, emotiontransfers (e.g., changing a face from a frown to a smile), statetransfers (e.g., aging a subject, reducing apparent age, changinggender), style transfers, graphical element application, and any othersuitable image or video manipulation implemented by a convolutionalneural network that has been configured to execute efficiently on theclient device 102.

In some examples, a computer animation model to transform image data canbe used by a system where a user may capture an image or video stream ofthe user (e.g., a selfie) using a client device 102 having a neuralnetwork operating as part of a messaging client application 104operating on the client device 102. The transformation system operatingwithin the messaging client 104 determines the presence of a face withinthe image or video stream and provides modification icons associatedwith a computer animation model to transform image data, or the computeranimation model can be present as associated with an interface describedherein. The modification icons include changes that may be the basis formodifying the user's face within the image or video stream as part ofthe modification operation. Once a modification icon is selected, thetransform system initiates a process to convert the image of the user toreflect the selected modification icon (e.g., generate a smiling face onthe user). A modified image or video stream may be presented in agraphical user interface displayed on the client device 102 as soon asthe image or video stream is captured, and a specified modification isselected. The transformation system may implement a complexconvolutional neural network on a portion of the image or video streamto generate and apply the selected modification. That is, the user maycapture the image or video stream and be presented with a modifiedresult in real-time or near real-time once a modification icon has beenselected. Further, the modification may be persistent while the videostream is being captured, and the selected modification icon remainstoggled. Machine taught neural networks may be used to enable suchmodifications.

The graphical user interface, presenting the modification performed bythe transform system, may supply the user with additional interactionoptions. Such options may be based on the interface used to initiate thecontent capture and selection of a particular computer animation model(e.g., initiation from a content creator user interface). In variousembodiments, a modification may be persistent after an initial selectionof a modification icon. The user may toggle the modification on or offby tapping or otherwise selecting the face being modified by thetransformation system and store it for later viewing or browse to otherareas of the imaging application. Where multiple faces are modified bythe transformation system, the user may toggle the modification on oroff globally by tapping or selecting a single face modified anddisplayed within a graphical user interface. In some embodiments,individual faces, among a group of multiple faces, may be individuallymodified, or such modifications may be individually toggled by tappingor selecting the individual face or a series of individual facesdisplayed within the graphical user interface.

A story table 312 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 304). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client 104 may include an icon that is user selectableto enable a sending user to add specific content to his or her personalstory.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client 104, to contribute content to aparticular live story. The live story may be identified to the user bythe messaging client 104, based on his or her location. The end resultis a “live story” told from a community perspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some examples, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

As mentioned above, the video table 314 stores video data that, in oneexample, is associated with messages for which records are maintainedwithin the message table 302. The video data may be video data capturedby a camera, as well as video data that resulted from screen recordinginitiated from a camera view user interface displayed by a messagingclient executing at a client device, in response to detecting activationof a screen recorder user selectable element. As explained above, thevideo data that resulted from screen recording initiated from a cameraview user interface does not include a recording of the user'sinteraction with the messaging client, as the messaging client at notime is in the foreground of the screen of the client device, at whichthe user is accessing the messaging client.

The image table 316 stores image data associated with messages for whichmessage data is stored in the entity table 304. The entity table 304 mayassociate various augmentations from the augmentation table 310 withvarious images and videos stored in the image table 316 and the videotable 314.

Data Communications Architecture

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some examples, generated by a messaging client 104 forcommunication to a further messaging client 104 or the messaging server114. The content of a particular message 400 is used to populate themessage table 302 stored within the database 120, accessible by themessaging server 114. Similarly, the content of a message 400 is storedin memory as “in-transit” or “in-flight” data of the client device 102or the application servers 112. A message 400 is shown to include thefollowing example components:

-   -   message identifier 402: a unique identifier that identifies the        message 400.    -   message text payload 404: text, to be generated by a user via a        user interface of the client device 102, and that is included in        the message 400.    -   message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400. Image data for a sent or received message 400 may        be stored in the image table 316.    -   message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102, and that is included in the message 400. Video data        for a sent or received message 400 may be stored in the video        table 314.    -   message audio payload 410: audio data, captured by a microphone        or retrieved from a memory component of the client device 102,        and that is included in the message 400.    -   message augmentation data 412: augmentation data (e.g., filters,        stickers, or other annotations or enhancements) that represents        augmentations to be applied to message image payload 406,        message video payload 408, or message audio payload 410 of the        message 400. Augmentation data for a sent or received message        400 may be stored in the augmentation table 310.    -   message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client 104.    -   message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   message story identifier 418: identifier values identifying one        or more content collections (e.g., “stories” identified in the        story table 312) with which a particular content item in the        message image payload 406 of the message 400 is associated. For        example, multiple images within the message image payload 406        may each be associated with multiple content collections using        identifier values.    -   message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   message sender identifier 422: an identifier (e.g., a messaging        system identifier, email address, or device identifier)        indicative of a user of the Client device 102 on which the        message 400 was generated and from which the message 400 was        sent.    -   message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The content of a particular message 400 may also include a message videosource 426 (“MSG_VIDEO_SRC”). The message video source 426 may be usedto indicate whether the video data in the message is video data capturedby a camera or whether the video data in the message resulted fromscreen recording initiated from a camera view user interface displayedby a messaging client executing at a client device, in response todetecting activation of a screen recorder user selectable element.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 316.Similarly, values within the message video payload 408 may point to datastored within a video table 314, values stored within the messageaugmentations 412 may point to data stored in an augmentation table 310,values stored within the message story identifier 418 may point to datastored in a story table 312, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 304.

Time-Based Access Limitation Architecture

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client 104. In one example,an ephemeral message 502 is viewable by a receiving user for up to amaximum of 10 seconds, depending on the amount of time that the sendinguser specifies using the message duration parameter 506.

In some examples, the ephemeral message 502 includes video data thatresulted from screen recording initiated from a camera view userinterface displayed by a messaging client executing at a client device,in response to detecting activation of a screen recorder user selectableelement. The source of the video data in the ephemeral message 502 beinga screen recording session initiated from a camera view user interfaceof a messaging client may be indicated in an associated component of theephemeral message 502, e.g., in the message video source 426(“MSG_VIDEO_SRC”) of FIG. 4.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message group 504 (e.g., a collection of messages in apersonal story, or an event story). The ephemeral message group 504 hasan associated group duration parameter 508, a value of which determinesa time duration for which the ephemeral message group 504 is presentedand accessible to users of the messaging system 100. The group durationparameter 508, for example, may be the duration of a music concert,where the ephemeral message group 504 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 508 when performing the setup and creation of the ephemeralmessage group 504.

Additionally, each ephemeral message 502 within the ephemeral messagegroup 504 has an associated group participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message group504. Accordingly, a particular ephemeral message group 504 may “expire”and become inaccessible within the context of the ephemeral messagegroup 504, prior to the ephemeral message group 504 itself expiring interms of the group duration parameter 508. The group duration parameter508, group participation parameter 510, and message receiver identifier424 each provide input to a group timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message group 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 514 operationally controls the overalllifespan of an associated ephemeral message group 504, as well as anindividual ephemeral message 502 included in the ephemeral message group504. In one example, each and every ephemeral message 502 within theephemeral message group 504 remains viewable and accessible for a timeperiod specified by the group duration parameter 508. In a furtherexample, a certain ephemeral message 502 may expire, within the contextof ephemeral message group 504, based on a group participation parameter510. Note that a message duration parameter 506 may still determine theduration of time for which a particular ephemeral message 502 isdisplayed to a receiving user, even within the context of the ephemeralmessage group 504. Accordingly, the message duration parameter 506determines the duration of time that a particular ephemeral message 502is displayed to a receiving user, regardless of whether the receivinguser is viewing that ephemeral message 502 inside or outside the contextof an ephemeral message group 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message group 504based on a determination that it has exceeded an associated groupparticipation parameter 510. For example, when a sending user hasestablished a group participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message group 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 504 when either the groupparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message group 504 has expired, or when theephemeral message group 504 itself has expired in terms of the groupduration parameter 508.

In certain use cases, a creator of a particular ephemeral message group504 may specify an indefinite group duration parameter 508. In thiscase, the expiration of the group participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message group504 will determine when the ephemeral message group 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage group 504, with a new group participation parameter 510,effectively extends the life of an ephemeral message group 504 to equalthe value of the group participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client 104) to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage group 504 to no longer be displayed within a user interface ofthe messaging client 104. Similarly, when the ephemeral timer system 202determines that the message duration parameter 506 for a particularephemeral message 502 has expired, the ephemeral timer system 202 causesthe messaging client 104 to no longer display an indicium (e.g., an iconor textual identification) associated with the ephemeral message 502.

FIG. 6 is a flowchart of a method 600 for facilitating screen recordingcamera mode. The method 600 may be performed by processing logic thatmay comprise hardware (e.g., dedicated logic, programmable logic,microcode, etc.), software, or a combination of both. Although thedescribed flowcharts can show operations as a sequential process, manyof the operations can be performed in parallel or concurrently. Aprocess may correspond to a method, a procedure, an algorithm, etc. Theoperations of methods may be performed in whole or in part, may beperformed in conjunction with some or all of the operations in othermethods, and may be performed by any number of different systems, suchas the systems described herein, or any portion thereof, such as aprocessor included in any of the systems. In one example embodiment,some or all processing logic resides at the client device 102 of FIG. 1and/or at the messaging server system 108 of FIG. 1.

The method 600 commences at operation 610, when the screen recordingsystem detects activation of the screen recorder user selectable elementin the camera view user interface. As explained above, when themessaging client is in the foreground of the screen of the clientdevice, the associated camera view user interface displays output of adigital image sensor of a camera provided with an associated clientdevice and also displays various user selectable elements, including thescreen recorder user selectable element, which is actionable to requestrecording of an output of a display system shown on a screen of theclient device. An example camera view screen 710 including a screenrecording user selectable element 732 is shown in diagram 700illustrated in FIG. 7. The camera view screen 710 includes a cameraactivation control 720 actionable to capture an image by the camera orto start and stop video recording. The camera view screen 710 alsoincludes a camera options panel 730 that may include various userselectable elements actionable to set respective camera modes, e.g., atimer mode or flash mode (not shown), as well as the screen recordinguser selectable element 732 actionable to request recording of an outputof a display system shown on a screen of the client device.

At operation 620, in response to detecting activation of the screenrecorder user selectable element in the camera view user interface, thescreen recording system removes the foreground focus from the messagingclient and causes commencing of the recording of the output of thedisplay system shown on the screen of the client device. When the screenrecording system removes the foreground focus from the messaging clientand causes commencing of the recording of the output of the displaysystem shown on the screen of the client device, the user interface ofthe messaging client is hidden from the view of the user.

In some examples, the screen recording system commences the recording ofthe output of the display system shown on the screen of the clientdevice only after having obtained a confirmation from the user. Thescreen recording system, in response to the detecting of the activationof the screen recorder user selectable element, generates a confirmationuser interface comprising a confirmation user selectable element. Inthis example, the screen recording system causes the recording of theoutput of the display system shown on the screen of the client deviceonly in response to detecting activation of the confirmation userselectable element. An example camera view screen that includes aconfirmation user interface 810 is shown in diagram 800 illustrated inFIG. 8. The confirmation user interface 810, in one example, includes a“RECORD” user selectable element 820 actionable to confirm the requestto commence screen recording and a “CANCEL” user selectable element 830actionable to retract the request to commence screen recording. Thescreen recording system commences the recording of the output of thedisplay system shown on the screen of the client device only in responseto detecting activation of the “RECORD” user selectable element 820.

The confirmation user interface 810 may also include a brief explanationthat the user can record their activity at the client device withrespect to various apps, while not being able to record any activityrelated to the messaging client itself, such as, e.g., the viewing ofephemeral messages configured to not persist after having been viewed bythe recipient. As explained above, this is achieved by backgrounding themessaging client prior the commencement of screen recording and bypausing or terminating screen recording whenever the screen recordingsystem detects a request to restore the foreground focus of the screenof the client device to the messaging client. A request to open themessaging client may be activation of a notification from the messagingsystem presented at the screen of the client device, a selection of themessaging client from one or more apps executing in the background atthe client device, or activation of the icon representing the messagingclient at the screen of the client device.

As explained above, once the screen recording starts, the output of thedisplay system shown on the screen of the client device is beingrecorded while the user is interacting with the client device, e.g., byplaying a game, checking the weather at a weather app, or reading thenews. The screen recording is automatically paused once the screenrecording system detects a request to bring to the foreground themessaging client. At operation 630, subsequent to the screen recordingsystem causing the recording of the output of the screen of the clientdevice, the screen recording system detects a request to restore theforeground focus of the screen of the client device to the messagingclient. At operation 640, in response to a detected request to open orto bring to the foreground the messaging client, the screen recordingsystem pauses the screen recording and opens the messaging client to thecamera view screen while concealing display of the output of a digitalimage sensor. In one example, the display of the output of the digitalimage sensor is concealed by overlaying the output of the digital imagesensor with a solid color overlay, which gives the viewer an impressionof a closed camera shutter.

The camera view screen, presented with the output of the digital imagesensor concealed, includes a dialog requesting the user to selectwhether to continue with the screen recording, by activating a firstuser selectable element, or to stop screen recording by activating asecond user selectable element. An example camera view screen thatincludes an example dialog 920 configured to obtain a user's instructionto resume or to stop screen recording is shown in diagram 900illustrated in FIG. 9.

The dialog 910, in one example, includes a “STOP” user selectableelement is actionable to terminate the recording of the output of thedisplay system shown on the screen and a “RESUME” user selectableelement is actionable to resume the recording of the output of thedisplay system shown on the screen. If the screen recording systemdetects the user's selection of resuming the screen recording, thescreen recording system once again removes the foreground focus of thescreen of the client device from the messaging client and resumes screenrecording. If the screen recording system detects the user's selectionof stopping the screen recording, the screen recording system stops thescreen recording and causes presentation, at the messaging client, auser interface for saving and/or editing of the video recorded duringthe screen recording process. The video of screen recording saved in themessaging system can be shared with other users of the messaging system.A result of the recording of the output screen may be saved in themessaging system as a screen recording video, and the user may bepermitted to share the screen recording video with other users. Forexample, the messaging system may detect a request submitted to themessaging client to communicate the screen recording video to arecipient in the messaging system and, in response to the request,communicate the screen recording video to the recipient.

Machine Architecture

FIG. 10 is a diagrammatic representation of the machine 600 within whichinstructions 608 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 1000 toperform any one or more of the methodologies discussed herein may beexecuted. For example, the instructions 1008 may cause the machine 1000to execute any one or more of the methods described herein. Theinstructions 1008 transform the general, non-programmed machine 1000into a particular machine 1000 programmed to carry out the described andillustrated functions in the manner described. The machine 1000 mayoperate as a standalone device or may be coupled (e.g., networked) toother machines. In a networked deployment, the machine 1000 may operatein the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine 1000 maycomprise, but not be limited to, a server computer, a client computer, apersonal computer (PC), a tablet computer, a laptop computer, a netbook,a set-top box (STB), a personal digital assistant (PDA), anentertainment media system, a cellular telephone, a smartphone, a mobiledevice, a wearable device (e.g., a smartwatch), a smart home device(e.g., a smart appliance), other smart devices, a web appliance, anetwork router, a network switch, a network bridge, or any machinecapable of executing the instructions 1008, sequentially or otherwise,that specify actions to be taken by the machine 1000. Further, whileonly a single machine 1000 is illustrated, the term “machine” shall alsobe taken to include a collection of machines that individually orjointly execute the instructions 1008 to perform any one or more of themethodologies discussed herein. The machine 1000, for example, maycomprise the client device 102 or any one of a number of server devicesforming part of the messaging server system 108. In some examples, themachine 1000 may also comprise both client and server systems, withcertain operations of a particular method or algorithm being performedon the server-side and with certain operations of the particular methodor algorithm being performed on the client-side.

The machine 1000 may include processors 1002, memory 1004, andinput/output I/O components 1038, which may be configured to communicatewith each other via a bus 1040. In an example, the processors 1002(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) Processor, a Complex Instruction Set Computing (CISC)Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, a processor 1006and a processor 1010 that execute the instructions 1008. The term“processor” is intended to include multi-core processors that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.10 shows multiple processors 1002, the machine 1000 may include a singleprocessor with a single-core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory 1004 includes a main memory 1012, a static memory 1014, and astorage unit 1016, both accessible to the processors 1002 via the bus1040. The main memory 1004, the static memory 1014, and storage unit1016 store the instructions 1008 embodying any one or more of themethodologies or functions described herein. The instructions 1008 mayalso reside, completely or partially, within the main memory 1012,within the static memory 1014, within machine-readable medium 1018within the storage unit 10110, within at least one of the processors1002 (e.g., within the Processor's cache memory), or any suitablecombination thereof, during execution thereof by the machine 1000.

The I/O components 1038 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1038 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 1038 mayinclude many other components that are not shown in FIG. 10. In variousexamples, the I/O components 1038 may include user output components1024 and user input components 1026. The user output components 1024 mayinclude visual components (e.g., a display such as a plasma displaypanel (PDP), a light-emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)), acousticcomponents (e.g., speakers), haptic components (e.g., a vibratory motor,resistance mechanisms), other signal generators, and so forth. The userinput components 1026 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and force of touches or touch gestures, or other tactile inputcomponents), audio input components (e.g., a microphone), and the like.

In further examples, the I/O components 1038 may include biometriccomponents 1028, motion components 1030, environmental components 1032,or position components 1034, among a wide array of other components. Forexample, the biometric components 1028 include components to detectexpressions (e.g., hand expressions, facial expressions, vocalexpressions, body gestures, or eye-tracking), measure biosignals (e.g.,blood pressure, heart rate, body temperature, perspiration, or brainwaves), identify a person (e.g., voice identification, retinalidentification, facial identification, fingerprint identification, orelectroencephalogram-based identification), and the like. The motioncomponents 1030 include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope).

The environmental components 1032 include, for example, one or cameras(with still image/photograph and video capabilities), illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment.

With respect to cameras, the client device 102 may have a camera systemcomprising, for example, front cameras on a front surface of the clientdevice 102 and rear cameras on a rear surface of the client device 102.The front cameras may, for example, be used to capture still images andvideo of a user of the client device 102 (e.g., “selfies”), which maythen be augmented with augmentation data (e.g., filters) describedabove. The rear cameras may, for example, be used to capture stillimages and videos in a more traditional camera mode, with these imagessimilarly being augmented with augmentation data. In addition to frontand rear cameras, the client device 102 may also include a 360° camerafor capturing 360° photographs and videos.

Further, the camera system of a client device 102 may include dual rearcameras (e.g., a primary camera as well as a depth-sensing camera), oreven triple, quad or penta rear camera configurations on the front andrear sides of the client device 102. These multiple cameras systems mayinclude a wide camera, an ultra-wide camera, a telephoto camera, a macrocamera and a depth sensor, for example.

The position components 1034 include location sensor components (e.g., aGPS receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1038 further include communication components 1036operable to couple the machine 1000 to a network 1020 or devices 1022via respective coupling or connections. For example, the communicationcomponents 1036 may include a network interface Component or anothersuitable device to interface with the network 1020. In further examples,the communication components 1036 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1022 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 636 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 636 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1036, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., main memory 1012, static memory 1014, andmemory of the processors 1002) and storage unit 1016 may store one ormore sets of instructions and data structures (e.g., software) embodyingor used by any one or more of the methodologies or functions describedherein. These instructions (e.g., the instructions 1008), when executedby processors 1002, cause various operations to implement the disclosedexamples.

The instructions 1008 may be transmitted or received over the network1020, using a transmission medium, via a network interface device (e.g.,a network interface component included in the communication components1036) and using any one of several well-known transfer protocols (e.g.,hypertext transfer protocol (HTTP)). Similarly, the instructions 608 maybe transmitted or received using a transmission medium via a coupling(e.g., a peer-to-peer coupling) to the devices 1022.

Glossary

“Carrier signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

“Client device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

“Communication network” refers to one or more portions of a network thatmay be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, a network or a portion of a network may include awireless or cellular network and the coupling may be a Code DivisionMultiple Access (CDMA) connection, a Global System for Mobilecommunications (GSM) connection, or other types of cellular or wirelesscoupling. In this example, the coupling may implement any of a varietyof types of data transfer technology, such as Single Carrier RadioTransmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

“Component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors 1004 orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“Computer-readable storage medium” refers to both machine-storage mediaand transmission media. Thus, the terms include both storagedevices/media and carrier waves/modulated data signals. The terms“machine-readable medium,” “computer-readable medium” and“device-readable medium” mean the same thing and may be usedinterchangeably in this disclosure.

“Machine storage medium” refers to a single or multiple storage devicesand media (e.g., a centralized or distributed database, and associatedcaches and servers) that store executable instructions, routines anddata. The term shall accordingly be taken to include, but not be limitedto, solid-state memories, and optical and magnetic media, includingmemory internal or external to processors. Specific examples ofmachine-storage media, computer-storage media and device-storage mediainclude non-volatile memory, including by way of example semiconductormemory devices, e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), FPGA, andflash memory devices; magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks Theterms “machine-storage medium,” “device-storage medium,”“computer-storage medium” mean the same thing and may be usedinterchangeably in this disclosure. The terms “machine-storage media,”“computer-storage media,” and “device-storage media” specificallyexclude carrier waves, modulated data signals, and other such media, atleast some of which are covered under the term “signal medium.”

“Non-transitory computer-readable storage medium” refers to a tangiblemedium that is capable of storing, encoding, or carrying theinstructions for execution by a machine.

“Signal medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

What is claimed is:
 1. A method comprising: in a messaging system thathosts a backend service for a messaging client, detecting an eventindicative of a request to restore a foreground focus of a screen of aclient device to the messaging client, wherein a recording of an outputof a display system shown on a screen of the client device is inprogress; and in response to the detecting, pausing the recording of theoutput of the display system shown on the screen.
 2. The method of claim1, comprising, in response to the detecting of the request to restorethe foreground focus of the screen of the client device to the messagingclient: restoring the foreground focus of the screen of the clientdevice to the messaging client by opening the messaging client to acamera view user interface configured to display output of a digitalimage sensor of a camera, the opening of the messaging client to thecamera view user interface comprises concealing display of the output ofa digital image sensor; and causing presentation of a first userselectable element actionable to terminate the recording of the outputof the display system and a second user selectable element actionable toresume the recording of the output of the display system.
 3. The methodof claim 2, comprising: detecting activation of the first userselectable element; and in response to the detecting of the selection ofthe first user selectable element, resuming the recording of the outputof the display system shown on the screen and removing the foregroundfocus of the screen of the client device from the messaging client. 4.The method of claim 2, comprising: detecting activation of the seconduser selectable element; and in response to the detecting of theselection of the second user selectable element, terminating therecording of the output of the display system shown on the screen. 5.The method of claim 2, wherein the concealing of the display of theoutput of the digital image sensor comprises overlaying the output ofthe digital image sensor with a solid color overlay.
 6. The method ofclaim 1, wherein the detecting of the event indicative of the request torestore the foreground focus of the screen of the client device to themessaging client is subsequent to generating a camera view userinterface including a screen recorder user selectable element actionableto request recording of the output of the display system shown on thescreen of the client device, the camera view user interface configuredto display output of a digital image sensor of a camera of the clientdevice.
 7. The method of claim 6, wherein the detecting of the eventindicative of the request to restore the foreground focus of the screenof the client device to the messaging client is subsequent to: detectingactivation of the screen recorder user selectable element at themessaging client having the foreground focus of the screen of the clientdevice; and in response to the detecting of the activation of the screenrecorder user selectable element, removing the foreground focus from themessaging client and causing recording of the output of the displaysystem shown on the screen of the client device.
 8. The method of claim1, wherein the detecting of the request to restore the foreground focusof the screen of the client device to the messaging client is detectingactivation of a notification from the messaging system, the notificationpresented at the output of the display system shown on the screen of theclient device.
 9. The method of claim 1, wherein the detecting of therequest to restore the foreground focus of the screen of the clientdevice to the messaging client is detecting activation of an iconrepresenting the messaging client, the icon presented at the screen ofthe client device.
 10. The method of claim 1, wherein the detecting ofthe request to restore the foreground focus of the screen of the clientdevice to the messaging client is detecting a selection of the messagingclient from one or more applications executing at the client device andlacking the foreground focus of the screen of the client device.
 11. Asystem comprising: one or more processors; and a non-transitory computerreadable storage medium comprising instructions that when executed bythe one or processors cause the one or more processors to performoperations comprising: in a messaging system that hosts a backendservice for a messaging client, detecting an event indicative of arequest to restore a foreground focus of a screen of a client device tothe messaging client, wherein a recording of an output of a displaysystem shown on a screen of the client device is in progress; and inresponse to the detecting, pausing the recording of the output of thedisplay system shown on the screen.
 12. The system of claim 11, whereinthe operations caused by instructions executed by the one or processorsinclude, in response to the detecting of the request to restore theforeground focus of the screen of the client device to the messagingclient: restoring the foreground focus of the screen of the clientdevice to the messaging client by opening the messaging client to acamera view user interface configured to display output of a digitalimage sensor of a camera, the opening of the messaging client to thecamera view user interface comprises concealing display of the output ofa digital image sensor; and causing presentation of a first userselectable element actionable to terminate the recording of the outputof the display system and a second user selectable element actionable toresume the recording of the output of the display system.
 13. The systemof claim 12, wherein the operations caused by instructions executed bythe one or processors include: detecting activation of the first userselectable element; and in response to the detecting of the selection ofthe first user selectable element, resuming the recording of the outputof the display system shown on the screen and removing the foregroundfocus of the screen of the client device from the messaging client. 14.The system of claim 12, wherein the operations caused by instructionsexecuted by the one or processors include: detecting activation of thesecond user selectable element; and in response to the detecting of theselection of the second user selectable element, terminating therecording of the output of the display system shown on the screen. 15.The system of claim 12, wherein the concealing of the display of theoutput of the digital image sensor comprises overlaying the output ofthe digital image sensor with a solid color overlay.
 16. The system ofclaim 11, wherein the detecting of the event indicative of the requestto restore the foreground focus of the screen of the client device tothe messaging client is subsequent to generating a camera view userinterface including a screen recorder user selectable element actionableto request recording of the output of the display system shown on thescreen of the client device, the camera view user interface configuredto display output of a digital image sensor of a camera of the clientdevice.
 17. The system of claim 16, wherein the detecting of the eventindicative of the request to restore the foreground focus of the screenof the client device to the messaging client is subsequent to: detectingactivation of the screen recorder user selectable element at themessaging client having the foreground focus of the screen of the clientdevice; and in response to the detecting of the activation of the screenrecorder user selectable element, removing the foreground focus from themessaging client and causing recording of the output of the displaysystem shown on the screen of the client device.
 18. The system of claim11, wherein the detecting of the request to restore the foreground focusof the screen of the client device to the messaging client is detectingactivation of a notification from the messaging system, the notificationpresented at the output of the display system shown on the screen of theclient device.
 19. The system of claim 11, wherein the detecting of therequest to restore the foreground focus of the screen of the clientdevice to the messaging client is detecting activation of an iconrepresenting the messaging client, the icon presented at the screen ofthe client device.
 20. A machine-readable non-transitory storage mediumhaving instruction data executable by a machine to cause the machine toperform operations comprising: in a messaging system that hosts abackend service for a messaging client, detecting an event indicative ofa request to restore a foreground focus of a screen of a client deviceto the messaging client, wherein a recording of an output of a displaysystem shown on a screen of the client device is in progress; and inresponse to the detecting, pausing the recording of the output of thedisplay system shown on the screen.